Clean up error handling to have less unexpected errors #529
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
We have a few inconsistencies in error handling:
--secret
Solution
This PR does a few things, but it most notably commits to using the errors defined in
errors.mjs
in our lib code. Through adding new exceptions and common patterns to convert 3rd party errors to things we expect, we can get rid of most unexpected errors.AuthenticationError
andAuthorizationError
. The 401 case has a default message to remove the inconsistent ones we have already.xxxxToCommandError
helpers: Simplified the existingthrowForError
function to just be a translation layer to catch the common error types across our dependencies.Result
Authentication errors and 4XX errors display consistently across the account, v4, v10, and schema APIs.
Testing
Add unit tests for the error mappings. Updated existing error tests.